This chapter describes Protocol Independent Multicast (PIM) messages. For information on message content and how to use the message, refer to the Introduction.
| PIM.001 |
Level: C-TRACE
Short Syntax: PIM.001 Add phyint IP_interface
Long Syntax: PIM.001 Add physical interface IP_interface
Description: PIM has been enabled on the specified physical interface.
| PIM.002 |
Level: C-TRACE
Short Syntax: PIM.002 Add tunnel tunnel_source-> tunnel_destination
Long Syntax: PIM.002 Add tunnel tunnel_source-> tunnel_destination
Description: A PIM tunnel has been configured between the given source and destination addresses.
| PIM.003 |
Level: U-TRACE
Short Syntax: PIM.003 Nbr IP_neighbor removed, ifc down
Long Syntax: PIM.003 Neighbor IP_neighbor removed due to interface going down
Description: The PIM virtual interface is going down and this neighbor has been removed from the neighbor list.
| PIM.004 |
Level: UE-ERROR
Short Syntax: PIM.004 bd hdr cks 0x checksum (exp 0x expected_checksum) source_ip_address -> destination_ip_address
Long Syntax: PIM.004 Bad header checksum 0x checksum (expected 0x expected_checksum) in packet from source_ip_address for destination_ip_address
Description: This message is generated when a PIM control message has an invalid checksum. The received checksum, together with the correct checksum, are displayed.
Cause: Most likely, this is a damaged packet. It may be that another node is building an incorrect PIM control message.
Action: If the problem persists, examine a line trace to determine where the packet is being damaged.
| PIM.005 |
Level: U-TRACE
Short Syntax: PIM.005 Rcvd PIM unk ver= PIM_version IP_source -> IP_destination, nt network ID
Long Syntax: PIM.005 Received PIM Unknown Version= PIM_version, IP_source -> IP_destination net network ID
Description: A PIM Control Message was received with an unknown version number. Packet is discarded.
| PIM.006 |
Level: P-TRACE
Short Syntax: PIM.006 Rcvd Hello Msg IP_source -> IP_destination, nt network ID
Long Syntax: PIM.006 Received PIM Hello Message, IP_source -> IP_destination net network ID
Description: A PIM Hello Message has been received.
| PIM.007 |
Level: P-TRACE
Short Syntax: PIM.007 Rcvd Jn/Prn Msg IP_source => PIM_upstream, nt network ID
Long Syntax: PIM.007 Received PIM Join/Prune Message, IP_source upstream PIM_upstream net network ID
Description: A PIM Join/Prune Message has been received. The displayed address is not the IP packet destination address, but the upstream router address contained in the PIM protocol packet.
| PIM.008 |
Level: P-TRACE
Short Syntax: PIM.008 Rcvd Assert Msg, grp IP_group, src IP_source, nt network ID
Long Syntax: PIM.008 Received PIM Assert Message, Group IP_group, Source IP_source, net network ID
Description: A PIM Assert Message has been received.
| PIM.009 |
Level: P-TRACE
Short Syntax: PIM.009 Rcvd Graft Msg IP_source -> IP_destination, nt network ID
Long Syntax: PIM.009 Received PIM Graft Message, IP_source -> IP_destination net network ID
Description: A PIM Graft Message has been received.
| PIM.010 |
Level: P-TRACE
Short Syntax: PIM.010 Rcvd GraftAck Msg IP_source -> IP_destination, nt network ID
Long Syntax: PIM.010 Received PIM Graft Ack Message, IP_source -> IP_destination net network ID
Description: A PIM Graft Acknowledgement Message has been received.
| PIM.011 |
Level: UE-ERROR
Short Syntax: PIM.011 Rcvd unk msg IP_source -> IP_destination, nt network ID
Long Syntax: PIM.011 Received PIM Unknown Message, IP_source -> IP_destination net network ID
Description: A PIM Control Message was received which has an unknown message type. The message is discarded.
| PIM.012 |
Level: P-TRACE
Short Syntax: PIM.012 Send Hello Msg IP_source -> IP_destination, nt network ID
Long Syntax: PIM.012 Sending PIM Hello Message, IP_source -> IP_destination net network ID
Description: A PIM Hello Message has been created and scheduled for transmission.
| PIM.013 |
Level: P-TRACE
Short Syntax: PIM.013 Send Jn/Prn Msg IP_source => PIM_upstream, nt network ID
Long Syntax: PIM.013 Sending PIM Join/Prune Message, IP_source upstream PIM_upstream net network ID
Description: A PIM Join/Prune Message has been created and scheduled for transmission. The displayed address is not the IP packet destination address (which is the all PIM router address, but the upstream router address contained in the PIM protocol packet.
| PIM.014 |
Level: P-TRACE
Short Syntax: PIM.014 Send Assert Msg, grp IP_group, src IP_source, nt network ID
Long Syntax: PIM.014 Sending PIM Assert Message, Group IP_group, Source IP_source net network ID
Description: A PIM Assert Message has been created and scheduled for transmission. The Assert occurs when a multicast data packet was received on an output interface for a multicast entry in the forwarding tables or having received an assert from another router which should not be forwarding the multicast data in question. This action signifies that duplicate multicast data is being sent due to routing loops. The assert message resolves which router should be the forwarding router and ensures this condition does not persist.
| PIM.015 |
Level: P-TRACE
Short Syntax: PIM.015 Send Graft Msg IP_source -> IP_destination, nt network ID
Long Syntax: PIM.015 Sending PIM Graft Message, IP_source -> IP_destination net network ID
Description: A PIM Graft Message has been created and scheduled for transmission.
| PIM.016 |
Level: P-TRACE
Short Syntax: PIM.016 Send GraftAck Msg IP_source -> IP_destination, nt network ID
Long Syntax: PIM.016 Sending PIM Graft Ack Message, IP_source -> IP_destination net network ID
Description: A PIM Graft Acknowledgement Message has been created and scheduled for transmission.
| PIM.017 |
Level: UI-ERROR
Short Syntax: PIM.017 Could not obtain iorb IP_source -> IP_destination
Long Syntax: PIM.017 Unable to obtain an iob for send, IP_source -> IP_destination
Description: No input/output request block (iorb) was returned by the system which was required by PIM to build and send a PIM control message.
Cause: The system has run out of resources. This usually occurs due to lack of system buffer memory.
Action: If not a problem due to an errant application, install more memory and assign more system buffers.
| PIM.018 |
Level: UI-ERROR
Short Syntax: PIM.018 Failed iorb send rqst IP_source -> IP_destination
Long Syntax: PIM.018 IORB send request was unsuccessful, IP_source -> IP_destination
Description: A request to send an iorb containing a PIM control message returned a failure and the message was discarded.
Cause: The system refused to send an input/output request block. This may be due to an overburdened router or a errant application.
Action: Upgrade to a higer performance router.
| PIM.019 |
Level: U-TRACE
Short Syntax: PIM.019 DR PIM_old_DR replaced by PIM_new_DR for nt network ID
Long Syntax: PIM.019 Designated Router PIM_old_DR is replaced by PIM_new_DR net network ID
Description: Designated Router timed out and is replaced by the new Designated Router.
| PIM.020 |
Level: C-TRACE
Short Syntax: PIM.020 Nbr PIM_neighbor del for int PIM_interface
Long Syntax: PIM.020 Neighbor PIM_neighbor Deleted from Interface PIM_interface
Description: The Neighbor timed out since it did not send Hello message on time and will be removed.
| PIM.021 |
Level: UI-ERROR
Short Syntax: PIM.021 No nbr blocks available for PIM_neighbor, int PIM_interface
Long Syntax: PIM.021 No neighbor control blocks are available for PIM_neighbor, Interface PIM_interface
Description: The neighbor array is full and no neighbor control blocks are available for the newly discovered neighbor on the interface.
Cause: The number of PIM neighbors has exceeded the limit supported by the PIM implementation. This may effect the designated router selection process.
Action: Reduce the number of routers running PIM on the same subnet.
| PIM.022 |
Level: C-TRACE
Short Syntax: PIM.022 Nbr PIM_neighbor added to int PIM_interface
Long Syntax: PIM.022 Neighbor PIM_neighbor added for Interface PIM_interface
Description: A neighbor was added to interface due to receiving a Hello message.
| PIM.023 |
Level: C-TRACE
Short Syntax: PIM.023 J/P Msg parsed, vif PIM_interface gcnt Group_count, jcnt Join_count, pcnt Prune_count
Long Syntax: PIM.023 Join/Prune message parsed, vif = PIM_interface, groups = Group_count, joins = Join_count, prunes = Prune_count
Description: A PIM Join/Prune formatted message has been received and parsed. The counts give the total number of groups, joins, and prunes that were parsed. The PIM virtual interface is the interface the packet was received on.
| PIM.024 |
Level: UI-ERROR
Short Syntax: PIM.024 No mem for msg q
Long Syntax: PIM.024 Could not allocate memory for building a message queue element.
Description: A memory allocation failure occurred when creating a message queue element for the PIM message queues.
Cause: The system has run low on resources and is out of system memory.
Action: Install more memory or upgrade router.
| PIM.025 |
Level: U-TRACE
Short Syntax: PIM.025 msg type unk, msg not queued
Long Syntax: PIM.025 Could not queue message element due to unknown message type.
Description: The message scheduler could not place the message element on the appropriate message queue due to an unknown message type passed by the caller. The message element is freed back to the memory pool and no other action taken.
| PIM.026 |
Level: UI-ERROR
Short Syntax: PIM.026 No mem for state, src = IP_source, grp = IP_group, vif = PIM_interface
Long Syntax: PIM.026 Could not get memory for state element, source= IP_source, group= IP_group, interface = PIM_interface
Description: A memory allocation failure occurred when creating a state element for the state database for the reported source group pair on the PIM interface shown.
Cause: The system has run low on resources and is out of system memory.
Action: Install more memory or upgrade router.
| PIM.027 |
Level: UI-ERROR
Short Syntax: PIM.027 No mem for sgnode, src = IP_source, grp = IP_group, vif = PIM_interface
Long Syntax: PIM.027 No memory for source-group node, source = IP_source, group = IP_group, interface = PIM_interface
Description: A memory allocation failure occurred when creating a source-group node element for the state database for the reported source group pair on the PIM interface shown.
Cause: The system has run low on resources and is out of system memory.
Action: Install more memory or upgrade router.
| PIM.028 |
Level: C-TRACE
Short Syntax: PIM.028 New PRUNE state src IP_source grp IP_group vif PIM_interface
Long Syntax: PIM.028 A new PRUNE state has been created, source = IP_source, group = IP_group, vif = PIM_interface
Description: A new PIM PRUNE state has been created and placed in the state database.
| PIM.029 |
Level: U-TRACE
Short Syntax: PIM.029 Del not required src IP_source grp IP_group vif PIM_interface
Long Syntax: PIM.029 Delete request for state not in database, source = IP_source, group = IP_group, vif = PIM_interface
Description: A request was processed to delete a state that does not exist in the PIM state database. No action was taken and control returned immediately to the caller.
| PIM.030 |
Level: C-TRACE
Short Syntax: PIM.030 PRUNE state removed src IP_source grp IP_group vif PIM_interface
Long Syntax: PIM.030 A PRUNE was deleted from the state database, source = IP_source, group = IP_group, vif = PIM_interface
Description: A PRUNE state has been successfully removed from the state database and removed from all the appropriate program queues. This PRUNE state now no longer exists.
| PIM.031 |
Level: UI-ERROR
Short Syntax: PIM.031 srte has rte type that is UNKNOWN by PIM, src net = IP_source type = route_type
Long Syntax: PIM.031 Unicast entry has route type UNKNOWN by PIM, source net = IP_source, route type = route_type
Description: PIM is attempting to determine local unicast routing metric preference for a particular multicast forwarding entry which is used in the PIM assert process. The route type of the unicast routing entry is not of any type known by PIM and the routing metric preference has been the 0x7FFFFFFF and the routing metric set to 0xFFFFFFFF, which are used for unknown routes. The result will usually lead to this router losing the assert process and pruning its oif from the multicast forwarding cache entry.
Cause: This is usually caused by running unicast routing protocols or other functions that update the unicast forwarding table that marks the unicast entry of a route type that PIM is not aware of. This should only occur if new protocols were added to the router and PIM implementation was not updated to support them. PIM may not be able to support the new functions or a newer version of PIM is required.
Action: Call customer support and inform them of problem. If all the unicast routing protocols and forwarding table modification mechanisms are supported by PIM, a new version is necessary.
| PIM.032 |
Level: P-TRACE
Short Syntax: PIM.032 Rcv Pim Control Msg for net network ID
Long Syntax: PIM.032 Received Pim Ctl Message for net network ID, which is not ready
Description: Received a PIM Control Message for an interface which is not ready to receive messages. The control message is discarded.
| PIM.033 |
Level: C-TRACE
Short Syntax: PIM.033 PIM states have been cleared
Long Syntax: PIM.033 The PIM state database has been cleared
Description: The PIM state database has thrown away all of its states. This is most commonly performed when the multicast forwarding cache has been thrown away due a unicast routing update.
| PIM.034 |
Level: U-TRACE
Short Syntax: PIM.034 Group address not multicast, addr = IP_group
Long Syntax: PIM.034 An invalid group address was encountered, address = IP_group
Description: During parsing of a PIM control message, a group address was encountered that did not qualify as a valid multicast address. The parser did not continue processing this address and ignored it, but continued further parsing of the packet.
| PIM.035 |
Level: U-TRACE
Short Syntax: PIM.035 jp rcv pkt len err, len error_length vif PIM_interface
Long Syntax: PIM.035 join/prune parser error due to bad PIM packet counts, length = error_length vif = PIM_interface
Description: While parsing a received PIM Join/Prune message, the parser discovered a length error. This occurs when the group, join, and prune count fields in the PIM packet itself is erroneous, reporting an incorrect number of group and source addresses contained in the packet.
| PIM.036 |
Level: C-TRACE
Short Syntax: PIM.036 New JOIN state src IP_source grp IP_group vif PIM_Interface
Long Syntax: PIM.036 A new JOIN state has been created, source = IP_source, group = IP_group, vif = PIM_Interface
Description: A new PIM PRUNE state has been created and placed in the state database.
| PIM.037 |
Level: C-TRACE
Short Syntax: PIM.037 JOIN state removed src IP_source grp IP_group vif PIM_Interface
Long Syntax: PIM.037 A JOIN was deleted from the state database, source = IP_source, group = IP_group, vif = PIM_Interface
Description: A JOIN state has been successfully removed from the state database and removed from all the appropriate program queues. This JOIN state now no longer exists.
| PIM.038 |
Level: U-TRACE
Short Syntax: PIM.038 No PIM vif, IP_source -> IP_destination, net network ID
Long Syntax: PIM.038 Could not find a PIM virtual interface, IP_source -> IP_destination net network ID
Description: A PIM control message has been received that could not be mapped to a PIM virtual interface. The packet is discarded.
| PIM.039 |
Level: UI-ERROR
Short Syntax: PIM.039 No mem for rpf q
Long Syntax: PIM.039 Could not allocate memory for building an rpf neighbor block.
Description: A memory allocation failure occurred when creating a reverse path forwarding neighbor control block.
Cause: The system has run low on resources and is out of system memory.
Action: Install more memory or upgrade router.
| PIM.040 |
Level: U-TRACE
Short Syntax: PIM.040 Rcv Assert for mfcache entry, no ifc, grp IP_group, src IP_source, fip fip_index
Long Syntax: PIM.040 Received Assert on interface not in mfcache entry, Group IP_group, Source IP_source, fip fip_index
Description: Received a PIM Assert message on the indicated multicast forwarding interface index. However, this interface is not present in the respective mfcache entry.
| PIM.041 |
Level: P-TRACE
Short Syntax: PIM.041 Rcv Assert for unk src, grp IP_group, src IP_source, fip = fip_index
Long Syntax: PIM.041 Received an Assert for unknown source, Group IP_group, Source IP_source, fip = fip_index
Description: Received a PIM Assert message on the indicated multicast forwarding interface index. However, the source address could not be located in the unicast routing table.
| PIM.042 |
Level: U-TRACE
Short Syntax: PIM.042 Discard packet due to bad addr, family = encode_family, type = encode_type
Long Syntax: PIM.042 Packet was discarded due to a bad address, family = encode_family, type = encode_type
Description: A PIM message packet has been received with an encoded address with either an unsupported family or type. The packet was discarded.
| PIM.043 |
Level: U-TRACE
Short Syntax: PIM.043 Bad addr, ignored, family = encode_family, type = encode_type
Long Syntax: PIM.043 Address in packet ignored due to bad address, family = encode_family, type = encode_type
Description: During parsing of a PIM control message, an encoded address was encountered with an unsupported family or type. Did not continue processing this address and ignored it, but continued further parsing of the packet.
| PIM.044 |
Level: U-TRACE
Short Syntax: PIM.044 Ignored aggregated addr, msklen = mask_length
Long Syntax: PIM.044 Ignored address with mask length less than maximum, mask length = mask_length
Description: During parsing of a PIM control message, an encoded address was encountered with a mask length less than the address maximum. This indicates aggregation, which is not supported by PIM, so the address was ignored.
| PIM.045 |
Level: U-TRACE
Short Syntax: PIM.045 Net net_index not pt-to-pt, reset hello to hello_period sec
Long Syntax: PIM.045 The net net_index is not a point-to-point, reset hello period to hello_period seconds
Description: When reading configuration information for a PIM interface, no hello period was specified to prevent the transmissions of hello messages after adjacency has occured. This is used for point to point interfaces only. If the interface being set up is not a point to point, the hello period is changed to the default hello period.